Yes, occasionally the lag may be caused by the LFS server, not by individual drivers, but that is a rare event connected with overall operating system behavior/installation. For any league races I always recommend to turn off all additional Airio checks, so that no one is spectated for lagging, indling, speeding, or kicked for bad language etc. To turn off all configured Airio checks type !ch off admin command. This also turns off auto restart. The !ch on command will get you back to previous configuration... 
There are three items in SRV file (meaning they can be different on each server) handling lagging:
First one turns on/off the lagging filter. Second one says what is a lag. Under default settings lag happens when the server is missing car info update for 400 ms. In that case one "point" is deduced from the number of allowed lags (third item). If there is more extensive lag, then double of initial value deduces one more "point", meaning lag of 800 ms means -2, lag of 1600 ms means -3 etc.
When half of total allowed lags is reached, the driver is warned that he is lagging. When total allowed number is reached, the driver is spectated for lagging. The default settings work pretty well, but you can of course specify a more tight lagging filter by e.g. specifying LagCount=2.
Airio also keeps lagging percentage for each driver, shown in the output of admin/limad !pl command. It is the last number on each line. In practice lagging around 1 percent is pretty heavy, it is hard to race with such a driver because he's disappearing or jumping around the track a lot.
# Remove cars with extensive lagging during race - boolean
CheckLagging=true
# Number of missing consecutive car position packets (sent every
# 100 ms) seen as lagging and maximum number of such lags before
# spectating - integers
LagCount=4
LagTotal=8First one turns on/off the lagging filter. Second one says what is a lag. Under default settings lag happens when the server is missing car info update for 400 ms. In that case one "point" is deduced from the number of allowed lags (third item). If there is more extensive lag, then double of initial value deduces one more "point", meaning lag of 800 ms means -2, lag of 1600 ms means -3 etc.
When half of total allowed lags is reached, the driver is warned that he is lagging. When total allowed number is reached, the driver is spectated for lagging. The default settings work pretty well, but you can of course specify a more tight lagging filter by e.g. specifying LagCount=2.
Airio also keeps lagging percentage for each driver, shown in the output of admin/limad !pl command. It is the last number on each line. In practice lagging around 1 percent is pretty heavy, it is hard to race with such a driver because he's disappearing or jumping around the track a lot.
Always glad to help.
And yes, colors are entered into config files just like that ^0 = black ^1 = red ^2 = green ^3 = yellow (then i'm not quite sure, just experiment a bit, but) ^7 = white, ^8 = gray, ^9 = gray + Latin charset (^L)...EDIT: LOL, Crady is so fast.
Note the ^9 in my answer however, that's not a widely known fact. But it is not much useful anyway. Basically, do not use ^9 in Airio config files, it may just mean adding 2 extra bytes...@ Kristi : Nice, waiting on MSN already.
@ jvalley : Airio stores points (and other data) on several levels. Two main levels are called "total" and "championship". Both can be deleted manually or automatically, which is done by default once a week with the championship data.
You may see championship (current week) points by typing !ptc. That gives you a list of the highest scores, all cars and tracks. You may also type !ptc bl1 or !ptc bl1+xfg to see champ data only for that track/car/combo. To see your own champ data use !pi or !pb, you'll also find your current position in the output.
Additionaly there are points for playing shown by !ptp and in !pi, newly also points for driving (!ptd and again !pi). These two may be used to gather points e.g. from only one server or only in certain periods, such as when a race thats part of some series is in progress. People may then see their points/position in the series only.
I'm not sure what you mean by "Also the language used to change the color for the messages". User messages in MSG files can be translated or updated, but colors put there as e.g. ^3 are ignored.
Create lines with several messages by either using one long like with "++" where a line break should be, or by using several same text keys, all except the 1st starting with "+", like:
TextKey=This is some text
TextKey=+This is 2nd line...
To use colors in defined text use LFS switches like ^1 for red or ^3 for yellow...
@ jvalley : Airio stores points (and other data) on several levels. Two main levels are called "total" and "championship". Both can be deleted manually or automatically, which is done by default once a week with the championship data.
You may see championship (current week) points by typing !ptc. That gives you a list of the highest scores, all cars and tracks. You may also type !ptc bl1 or !ptc bl1+xfg to see champ data only for that track/car/combo. To see your own champ data use !pi or !pb, you'll also find your current position in the output.
Additionaly there are points for playing shown by !ptp and in !pi, newly also points for driving (!ptd and again !pi). These two may be used to gather points e.g. from only one server or only in certain periods, such as when a race thats part of some series is in progress. People may then see their points/position in the series only.
I'm not sure what you mean by "Also the language used to change the color for the messages". User messages in MSG files can be translated or updated, but colors put there as e.g. ^3 are ignored.
Create lines with several messages by either using one long like with "++" where a line break should be, or by using several same text keys, all except the 1st starting with "+", like:
TextKey=This is some text
TextKey=+This is 2nd line...
To use colors in defined text use LFS switches like ^1 for red or ^3 for yellow...
Aaaah, right, so the /pass= is not an ideal example of usable command.
Sorry for that, I believe this explains some earlier troubles you mentioned.Well, errors are bad.
They are always captured and reported, but some routines do not complete because of errors. In most cases it wont hurt much, but it may lead to unexpected bahavior in other situations. I'm trying to deal with every single error that appears in the application, however rare and unimportant it may be, and however smoothly it is dealt with. Airio system log is marvelous tool for this.Due to recent updates (and because I do not keep old source code), I'm not able to say where exactly the error appears, but there are in fact only two candidates: 1) Please check the TimedMotd items in SRV file(s), make sure they're not too long. 2) If you're running some external script regularly, check its output (returned to Airio for processing) for length. Or try stopping the script (see ScriptTimed in SRV) and watch if that error suddenly disappears.
Again note that this "string length limit" bug is removed from Airio 2.2.7, entered and used strings can have any length.
This is a thing that I discovered only recently and corrected in the latest 2.2.7 compile. The error means (probably) you're trying to handle strings larger than 256 bytes/characters. Make sure you're not using such extensive text in config files for now (and when possible, update to the latest 2.2.7). But it is strange the error appeared suddenly, if you did not make any config changes...
Indeed.
Uhm, sounds kind of complicated. But certainly something along those lines can be implemented.
Right, simply taking MSG (or SET, maybe others in the future) files from root and overwriting the existing files in subfolder is not always the expected and desired behavior. I think I'll remove the default SET file completely from the archive, I'll just leave mention about its possible use in the configuration suggestions.
But files in root must take precedence and must be moved to subfolders because of other features. The best way to ensure you'll not lose your work suddenly is, in my view, renaming the existing files before copying new ones. Thus the required behavior is preserved and even after erroneous update you have the option to delete/rename files and use previous configuration.
Worth mentioning is the fact that FULL version creates daily backup of all TXT (configuration, stats, log) files, optionally sending it to other FTP location. Reverting to old config including customized messages or broken stats is then easy.
You're completely right, all SET, MSG, LOG, and ZIP files found in Airio root folder on start, reload, and some other actions are simply copied to appropriate subfolders, overwriting the existing files. That's usually the required and expected behavior, say in case of updating MSG files from new language pack. But you're also right sometimes this may lead to certain issues, such as with the default SET file.
Now there's the question about what can be done. The easiest solution is not to copy default SET file from the updated Airio archive. Take just EXE and PBD, and also check what's new in standard config files, that is CFG, TCD, and SRV.
Another option would be to automatically create a backup copy of files already existing in subfolders in case new files with the same name are found in root. But they really need to be copied and must take precedence over the existing files, or some other features (such as remote updating using !dld command) will cease to function.
Now there's the question about what can be done. The easiest solution is not to copy default SET file from the updated Airio archive. Take just EXE and PBD, and also check what's new in standard config files, that is CFG, TCD, and SRV.
Another option would be to automatically create a backup copy of files already existing in subfolders in case new files with the same name are found in root. But they really need to be copied and must take precedence over the existing files, or some other features (such as remote updating using !dld command) will cease to function.
Just a quick note: Airio 2.2.7 has been updated a bit (one small bug fix, solving a possible issue). To use it just download the archive again and update EXE and PDB files.
Please also note there are for some time already new/updated language files available. You can update the existing language files just by extracting new MSG files into Airio folder and typing the !rld command, no Airio restart is necessary.
Especially if you choose some other language than English as the default language (assigned to new drivers and to the server itself), make sure you use the latest translations. I saw Finnish language used by default, but because obsolete and incomplete language files were used, the output did not look particularly good.
Please also note there are for some time already new/updated language files available. You can update the existing language files just by extracting new MSG files into Airio folder and typing the !rld command, no Airio restart is necessary.
Especially if you choose some other language than English as the default language (assigned to new drivers and to the server itself), make sure you use the latest translations. I saw Finnish language used by default, but because obsolete and incomplete language files were used, the output did not look particularly good.
Airio 2.2.7 is released, again improving some older things and adding new ones.
It is not a command, people need to click on the Server Rules button in the personal preferences screen displayed by pressing Shift+i.
Fantastic! Haven't tested it myself yet but I'll certainly do that. Thanks, Michele, for your work & development.
In my view the question is why use some external ban file. You can ban all those usernames just once for a looong time and then backup the server BAN file and use it in case system is reinstalled.
If you really for some reason want to use an external file, you may actually create a SET file with specific !ban commands and run that file manually using the !si command.
FULL version adds two features usable in this case: 1) The !ban commands may be optionally sent to all connected servers, so that only one SET file is needed. 2) Using scheduled actions this file may be invoked in regular intervals, say once a day.
In the FREE version it is not possible to propagate !ban (and !unban) commands to all servers and also it is not possible to create one common SET file usable by all servers. Unless you're using one common LFS ban file on all servers, which is possible, you'd need to create 4 separate SET files.
A hint: The servers would use one common ban file, if they are run from the same directory, using different cfg files (LFS files, not Airio). In this arrangement all bans and unbans are common, valid immediatelly on all servers...
If you really for some reason want to use an external file, you may actually create a SET file with specific !ban commands and run that file manually using the !si command.
FULL version adds two features usable in this case: 1) The !ban commands may be optionally sent to all connected servers, so that only one SET file is needed. 2) Using scheduled actions this file may be invoked in regular intervals, say once a day.
In the FREE version it is not possible to propagate !ban (and !unban) commands to all servers and also it is not possible to create one common SET file usable by all servers. Unless you're using one common LFS ban file on all servers, which is possible, you'd need to create 4 separate SET files.
A hint: The servers would use one common ban file, if they are run from the same directory, using different cfg files (LFS files, not Airio). In this arrangement all bans and unbans are common, valid immediatelly on all servers...
Well, I'm not a Linux guru, but the FromBinary method is in Airio for many months now and nobody reported troubles with that. So my guess would be you need to add some other Mono packages or update Mono. People running Airio under Linux use these mono packages: mono-runtime, libmono-corlib2.0-cil, libmono-system2.0-cil. I hope this helps...
Airio 2.2.6 is released, containing some of the above mentioned fixes (timed messages, format of exported time, ZIP library used). New is !results or just !rs command showing last race results by car categories. It is also possible now to use IncludeFile directive in SRV and CFG files allowing config file customizations. Completely removed is support for 2.1.8 and lower versions configuration files (such as Airio.cfg.nc.txt, Airio.cfg.lc.txt, and Airio.cfg.tc.txt). These are completely ignored to address some confusion and unexpected behavior. See the changelog for more information.
All your suppositions are correct, I believe. The timer to call default server SET file starts when last driver disconnects. So if that server was empty when you did the config changes, the timer never starts and never calls the SET file. Try connecting there, disconnecting and watch Airio system log. This feature should work, it did last time I checked.
All your suppositions are correct, I believe. The timer to call default server SET file starts when last driver disconnects. So if that server was empty when you did the config changes, the timer never starts and never calls the SET file. Try connecting there, disconnecting and watch Airio system log. This feature should work, it did last time I checked.
Last edited by EQ Worry, .
Ahh, cool, I'll try to grab some points then. Still the TBO class is sooo distant for me... 
Still the TBO class is sooo distant for me... Well, I would not be surprised if it won't work with Asian characters. Airio currently does not convert any Asian characters to Unicode, it leaves them in the original form. So, you may try to copy the team tag as it appears in Airio log file and see if that works.
I'm not sure what "blade" is here, but I get the meaning. Basically, Airio manages each connection to server individually, regardless of all other connections. A server (or group of servers) goes offline, their connections will close, the remaining will go on unperturbed. All connections may be broken, Airio would still run. With current state of things Airio will try to connect back to each disconnected server every 5 minutes, until the appropriate CON file is removed and the LFS server is back online and reachable. I may change this though to give it like 3 reconnect attempts andthen give up.
For anyone interested you should know the IP capturing is supported in FULL version only. I've been thinking about banning by IP several times, for now always shrinking away from the idea. Until patch Z the banning (and kicking) was done in demo using IP only, but it lead to unwelcome behavior, when wrong people were kicked (just because they used the same IP) and several drivers using the same provider (and one shared IP) were banned at once. Try running the doubled IP address filter and see in how many kicks this results, how many addresses are shared. Basically, I see banning by IP as giving more troubles than advantages.
With many items in CFG file this is clearly not possible, because they cover things common to the running instance, such as stats handling, external communications, language filter. With other items there it may be possible, but I fear it would complicate the setup. For example having different limads on different servers may be sometines desired, but it is really rather an exception. By definition the CFG file contains items common to one running instance, any server-depentant items would need to be moved to SRV file which is quite large even as it is.
With the TCD file the situation is somewhat similar, because they are track/car data common to the running instance. You may certainly see that having absolute freedom with the option to define these things differently on every server may be needed sometimes, but I wouldn't want to solve the configuration issues resulting from this. In case of step spin detection you mention you always have the option to activate that filter on one server and deactivate on another. But you're right, you cannot have two different values currently.
I'll give the TCD file yet some thought, see what items can be doubled in SRV file (such as DefaultCar is). I also feel some SRV items should be actually track/car dependant, e.g. to allow giving more points for driving with more demanding cars...
Hmmm, this look rather like incorrect configuration in the TCD file, with old value still applied somehow. Or it is because that FXR is then seen as FX2, one of the default-defined custom cars. Either remove that definition or disallow FX2 on appropriate server.
@ Hotmail : Ah, you're right about the times, my bad. 2.2.6 contains a fix, time is exported in 24 hour format.
@ Michele : To say the truth, I'm not sure the PHP script will work if specified this way, I'm really not sure. I'd expect a Web address there, but maybe if the local system is configured in some way to handle PHP files. About sharing the script, it is always great to have something to start with. And about export filter, there is no such thing, export to PB.txt (Lapper) file is always complete.
@ Framaris : Cool it works and LOL at your rusty French. As for 500servers, I'm not the one updating Airio there, I believe Franky does that when somebody requests an update. I guess I'll try to contact him and come up with some better arrangement so that the updates are available sooner.
@ Deslotted : Very nice, I've been playing with a Twitter library a bit, some basic updates are working in 2.2.6 being prepared now. But I'm thinking about just updating certain entries (such as who is online now, and what is the current server state), not creating new ones. This would require more testing though and also seeing what the "spamming" limits are.
@ Crady : Yup, you're right, not everyone is interested in both split and sector data. I'll see what can be done about it, a multifunction button comes to mind, turning on both, just splits, just sectors, and none...
@ Michele : To say the truth, I'm not sure the PHP script will work if specified this way, I'm really not sure. I'd expect a Web address there, but maybe if the local system is configured in some way to handle PHP files. About sharing the script, it is always great to have something to start with. And about export filter, there is no such thing, export to PB.txt (Lapper) file is always complete.
@ Framaris : Cool it works and LOL at your rusty French. As for 500servers, I'm not the one updating Airio there, I believe Franky does that when somebody requests an update. I guess I'll try to contact him and come up with some better arrangement so that the updates are available sooner.
@ Deslotted : Very nice, I've been playing with a Twitter library a bit, some basic updates are working in 2.2.6 being prepared now. But I'm thinking about just updating certain entries (such as who is online now, and what is the current server state), not creating new ones. This would require more testing though and also seeing what the "spamming" limits are.
@ Crady : Yup, you're right, not everyone is interested in both split and sector data. I'll see what can be done about it, a multifunction button comes to mind, turning on both, just splits, just sectors, and none...
Turkey, you're right it is strange the newer file is ignored. I wanted to have some backwards compatibility, but obviously it leads rather to confusion than advantage. In the next version I'll remove the support for old config files completely. It will make the code cleaner and the causes of Airio misbehavior more obvious as well.
Crady, I guess you're right the created ZIP file is not quite OK. It works e.g. in WinRar, but only for extraction. If you add something, the archive is suddenly broken. The problem is I use external library for creating ZIPs, so I'll need to look closer at the settings used or other available options or newer version...
Deslotted, well that constant messages are not nice, certainly. They are very probably caused by some strange server time lock settings, with the status changing every minute. Check your time lock setting in SRV file, tell me what you're using now, switch to defaults until I see what's going on there...
Crady, I guess you're right the created ZIP file is not quite OK. It works e.g. in WinRar, but only for extraction. If you add something, the archive is suddenly broken. The problem is I use external library for creating ZIPs, so I'll need to look closer at the settings used or other available options or newer version...
Deslotted, well that constant messages are not nice, certainly. They are very probably caused by some strange server time lock settings, with the status changing every minute. Check your time lock setting in SRV file, tell me what you're using now, switch to defaults until I see what's going on there...
Hi, there, this is just a quick drop from me before I'm again fully online:
@ bunder9999 : As far as I know there's no rules appearing only when someone connects first time. All connect items (big and smaller buttons) appear on every connect, if defined. Displaying Shif+i (preferences) menu by default on connet is a tricky matter. I had it implemented that way but it was causing too many connect failures. It is, after all, almost 100 buttons to be sent to a barely established connection. There could be a delay set, but I feel regular LFS people start to know the system and I'd really love to keep its default actions, that cannot be turned off, to a minimum.
@ Framaris : Having a FR version would be most cool. It is not an easy job though, with almost 500 messages (very short to rather long) to translate; my estimate is it may take up to 2 hours. Just download the latest language pack (for 2.2.x) and see the EN file to get better estimate.
# Rules, FAQ, Notes : In 2.1.7 there was a change in how these items are specified. No more external files (Airio.txt.rl.txt..) are used, the lines are put into Airio.cfg.txt file just like other items. Here I dare to quote from the changelog:
"Also the text lines from TXT.FQ, TXT.RL, and TXT.NT were moved into a new section of Airio.cfg.txt, with new items TextFAQs, TextNotes, and TextRules available. The old arrangement in NOT supported, the three formerly used TXT files are ignored. Any changes in FAQ/Notes/Rules buttons need to be updated by !rld, just like all other items."
So, if you had a text like this in Airio.txt.rl.txt file:
Here are the server rules:
Always observe the rules,
never use any cheats!
You would copy them into Airio.cfg.txt file and add appropriate keys:
TextRules=Here are the server rules:
TextRules=Always observe the rules,
TextRules=never use any cheats!
Note there are no opening pluses (+). After updating save the CFG file, delete old RL, FQ, and NT files, type !rld and it should be functional. If not, it may be caused by another catch: If you still have files like Airio.cfg.tc.txt or Airio.cfg.nc.txt in Airio folder, the new merged Airio.cfg.txt will actually be ignored, the items just added never read! To solve the trouble I'd suggest you switch completely to the new file structure, 2 months old now, no more changes planned.
I'm very sorry, I know it is not pleasant to change the config files used, but as Airio was developing, people were losing their way among the various config files. With the current 3 main config files I believe a reasonable balance between the number of files and their size was achieved.
Basically, if you're doing updates from version 2.1.8 or below to the current version, I'd suggest you start with new default config files as they are offered in the downloaded archive, going through the items and copying there values from your old config files. All updates (such as in text items) are then guaranteed to function and further updates will be much easier, because they mean only copying a few lines/items, as they are mentioned in the changelog.
@ Crady : Sorry, I can't help you with unzipping, PHP is not my field. The same is true concerning the live stats. But I must say it is a useful feature, if supported by PHP knowledge. You may take a look in here about the data available: http://racingteam.aa24.net/stats/servers.php. You may also try contacting JoRuss, author of the script, using LFS Forum private message...
@ bunder9999 : As far as I know there's no rules appearing only when someone connects first time. All connect items (big and smaller buttons) appear on every connect, if defined. Displaying Shif+i (preferences) menu by default on connet is a tricky matter. I had it implemented that way but it was causing too many connect failures. It is, after all, almost 100 buttons to be sent to a barely established connection. There could be a delay set, but I feel regular LFS people start to know the system and I'd really love to keep its default actions, that cannot be turned off, to a minimum.
@ Framaris : Having a FR version would be most cool.
It is not an easy job though, with almost 500 messages (very short to rather long) to translate; my estimate is it may take up to 2 hours. Just download the latest language pack (for 2.2.x) and see the EN file to get better estimate.# Rules, FAQ, Notes : In 2.1.7 there was a change in how these items are specified. No more external files (Airio.txt.rl.txt..) are used, the lines are put into Airio.cfg.txt file just like other items. Here I dare to quote from the changelog:
"Also the text lines from TXT.FQ, TXT.RL, and TXT.NT were moved into a new section of Airio.cfg.txt, with new items TextFAQs, TextNotes, and TextRules available. The old arrangement in NOT supported, the three formerly used TXT files are ignored. Any changes in FAQ/Notes/Rules buttons need to be updated by !rld, just like all other items."
So, if you had a text like this in Airio.txt.rl.txt file:
Here are the server rules:
Always observe the rules,
never use any cheats!
You would copy them into Airio.cfg.txt file and add appropriate keys:
TextRules=Here are the server rules:
TextRules=Always observe the rules,
TextRules=never use any cheats!
Note there are no opening pluses (+). After updating save the CFG file, delete old RL, FQ, and NT files, type !rld and it should be functional. If not, it may be caused by another catch: If you still have files like Airio.cfg.tc.txt or Airio.cfg.nc.txt in Airio folder, the new merged Airio.cfg.txt will actually be ignored, the items just added never read! To solve the trouble I'd suggest you switch completely to the new file structure, 2 months old now, no more changes planned.
I'm very sorry, I know it is not pleasant to change the config files used, but as Airio was developing, people were losing their way among the various config files. With the current 3 main config files I believe a reasonable balance between the number of files and their size was achieved.
Basically, if you're doing updates from version 2.1.8 or below to the current version, I'd suggest you start with new default config files as they are offered in the downloaded archive, going through the items and copying there values from your old config files. All updates (such as in text items) are then guaranteed to function and further updates will be much easier, because they mean only copying a few lines/items, as they are mentioned in the changelog.
@ Crady : Sorry, I can't help you with unzipping, PHP is not my field. The same is true concerning the live stats. But I must say it is a useful feature, if supported by PHP knowledge. You may take a look in here about the data available: http://racingteam.aa24.net/stats/servers.php. You may also try contacting JoRuss, author of the script, using LFS Forum private message...
Well, yes, that's true, version 2.2.5 is available for several days now.
Not as many interesting changes there though.More important is the new available language pack. Thanks to other dedicated people there are now complete localized Airio 2.2.x user messages available in the following languages: CZ, RU, PL, SP, CA, GE, FI, SE. Also the following languages maybe updated/added soon: NL, HU, GR, EE, LT, PT. I've had reports about IT translation being prepared, but it never materialized so I do not know the stage of that localization.
What I miss most is the FR translation, which hits me as strange. I know the French are proud of their language, yet none was found so far to be willing to promote his language and servers using Airio.
To install the new languages just unzip the archive and copy all the MSG files into Airio folder. Type !rld if Airio is already running and check by pressing Shift+i the new definitions are loaded.
What it does not show are Japanese/Korean/Chinese characters, other special characters used in European languages should be displayed correctly. Airio currently does not convert the above mentioned characters into their Unicode equivalent and back, it basically ignores them. Also note that having J/K/C characters on a Web page would require to have that language installed, for many people it would just generate unwelcome "language pack installation required" browser messages.
Yes, I've been thinking about this (just as about requiring cars to stop and give way if they're returning from pits and there's traffic), but these are not easy matters, they must cover many different situations, be easily configurable yet sufficiently flexible. But in time I'll surely try to get these things running, they could be good protection/nice addition things.
One last note: I'm leaving now for 2 weeks on a family holiday. I may occasionally see my mail, but I will not be able to solve troubles or respond promptly to any questions and other issues. So please bear with me for 2 weeks now, when I'm back I'll try to provide again all support I'm capable of.
OK, I'll mention to Fail the option to have the spinning filter running only on SO tracks and nowhere else (or as he sees fit). After all, it is a matter of one minute config update, all done live on running server.
First, thanks J@tko for your responses. And you're of course right, not every restricted area is Airio-defined one. By default restricted/limited areas are defined only on BL1 and BL2 tracks, because they are more flexible than LFS-defined ones. (For example XFG and XRG cars would be spectated when trying to cut the chicane, while FBMs can pass there because for that car there are no time gains achieved by cutting, it is just escape route.)
There are also servers (I believe also the Suomi ones), which are running the so-called Remote+ version. Remote+ defines other areas (such as around the chicane on BL1) that would warn/spec you. Again, that's not Airio business.
I would almost agree on that one.
It is kind of depressing that once you start spinning you can just wait if you'll get spectated or if you'll escape that filter and will be able to continue.But then we must see that races with 32 cars are no exception on that server and spectating fast every quickly spinning car has its obvious advantages. In the end, as you mentioned, it is admin decision, if this filter will run and under what setting.
I might just call to Failure's attention that this filter may have different setting on every track (or car, or both). Very usable in SO track with narrow path, not so much on WE and elsewhere with wide escape zones and barriers far away.
Last edited by EQ Worry, .
Ahh, nice post, Benjie, lets take a look at it.
Completely wrong. Under default setting idling is set to 30 seconds. 5 seconds would be impossible to have, people will get specced right at the start before green light comes on and that really does not happen. So you're obviously wrong here.
Default settings define 2 restricted areas on BL1, the most important is on the inside of turn 1, the grass area there. It may hurt you once, it will save your race ten more times when people are sliding on grass (or going there on purpose) after start and crash the whole field. So, honestly, that's no crap, the gains are very high comparing to losses. How many cars would you have hit if you were not spectated? Maybe none, maybe ten, we do not know.
You have to go wrong way for 5 seconds in fact (and that is active movement in the wrong way, covering significant distance, not just a few meters), that is in race and under default settings. Most people need much less to turn their car around and get back on the track. Only crashers will not like this setting, because it makes their life so much harder.
Overall, EVERYTHING in Airio is admin-configurable. So if you think some settings are very wrong, ask server admins to change them. But the default demo settings, which I gather most servers use, have been tuned for many months. They are made so that decent racing is supported and so that crashers have a hard time (restricted areas in favorite crash spots, short allowed wrong way driving, many other filters). Strange you have problems with these primary protections. But take no offence.
Airio allows admins to create highly restrictive environment - say no bad words allowed, only one race join allowed, certain lap time required to join the race, etc. All these filters/check can also be turned off to create a very lenient environment - Airio then only gathers timing and other personal data, manages start grid, etc.
The default settings that are part of Airio download are something in between. Not all checks are active, not all defined, but some that has shown their value in the past are by default active. They may hurt you once, they may serve you in many other situations.
There's for example the blue flag check, people were complaining to me as to an AirAttack admin that it is a stupid filter. If someone has blue flag and the obstructed driver is close behind him, the flagged drivers may be getting requests to let the driver behind pass. If he ignores say 4 such warnings, he is spectated for bad driving. True, it may hurt when you're trying to unlap yourself and when you're not fast enough to put some space between yourself and the leader, but most of the time, when you're doing a good race (not rejoining in lap 3 from pits), it will help you, make the way clear for you from people unwilling to give way.
Sooo, every filter/check is a double-sided sword. I believe 95 percent of drivers would agree though that the default settings are very reasonable, supporting good racing, punishing only when there's a reason. Note that you're never speced/kicked for good driving. All the troubles you mentioned were results of your mistakes/crashes. That by itself tells a lot.
It means there was a problem communicating with server, the conection was broken. Usually this happens when the server goes offline temporarily or restarts itself. Airio then closes the connection and tries to make a new one every 5 minutes.
LFSW data cannot be received for people that expressedly blocked them in their LFS World settings. You'll see the message about not receiving LFSW data for people with blocked access or without any data.
Use 360, spinning direction does not matter. Negative numer actually allows any spin speed.
That would be because of track rotation set. When last driver leaves the server, it is like voting to end race. If defined, track rotation will be done. See RotateTracks in SRV file.
This is active by default, see the following items in SRV file:
CheckDriving=true
WrongDrivingTimeRace=5
WrongDrivingTimePrac=10
Last edited by EQ Worry, .
FGED GREDG RDFGDR GSFDG